Task: Define The Infrastructure (MTP)
Purpose
Determining the infrastructure required for the test process at an early stage, in particular the parts that must be set up for multiple test levels or have a relatively long order time.
Relationships
RolesPrimary: Additional: Assisting:
Outputs
Main Description

Method of operation

The method consists of the following sub-activities:

  1. Defining the test environment
  2. Defining test tools
  3. Defining the office setup
  4. Establishing the infrastructure planning.

Products

The description of the required infrastructure at the overall level, including planning, laid down in the master test plan.

Techniques

  • Checklist “Office setup”
  • Checklist “Test environment”
Steps
1. Defining the test environment

Every test level requires a test environment to execute the tests. This environment is roughly composed of the following components:

  • Hardware
  • Software
  • Communication resources
  • Facilities to create and use files
  • Procedures

The environment must be composed and set up in such a way that it can be optimally determined, on the basis of the test results, in how far the test object complies with the defined requirements. The environment has a significant impact on the quality, lead time and costs of the test process.

To manage the environment correctly, it is therefore often separate from the development or production environment. Every test level has different requirements for the test environment. As a rule of thumb, the early tests – such as the development tests – have a greater need for a flexible environment that is easy to adapt. Later tests, such as the acceptance test, are more in need of stability and representativeness. Thus, the development tests are usually executed in the Development Environment, the system test in its own Test Environment, the acceptance tests in an Acceptance Environment, just before the actual Production Environment. This is also called the DTAP model (section 8.4.5 “DTAP model”).

Www.tmap.net contains a checklist that can be useful to establish the test environment.

When the test environments already exist, e.g. in a maintenance situation, they only need to be referred to and any required changes specified.

2. Defining test tools
The required test tools are defined roughly. Test tools can provide support for most test activities. The focus for the master test plan is on the tools that can be used for multiple test levels. Examples are test management, capture & playback, defects administration and simulation tools.
3. Defining the office setup
The office infrastructure (work spaces, meeting rooms, telephones, PCs, network connections, office software, printers, etc) required for testing is defined in outline. This means office setup in the broadest sense since the testers must be able to do their work under good conditions. A checklist for office setup can be found on www.tmap.net.
4. Establishing the infrastructure planning
For all of the required parts of the infrastructure, it is determined who is responsible for their elaboration, selection and acquisition. Agreements are recorded. An overall planning is also created with the times at which the various facilities must be available.
More Information
Checklists
Guidelines

Copyright © 2006, Sogeti Nederland B.V. All rights reserved.